Loading models on nodes having multiple model service frameworks

ABSTRACT

This disclosure relates to model loading. In one aspect, a method includes determining, based on a preset execution script and resource information of multiple execution nodes, loading-tasks corresponding to the execution nodes. Each execution node is deployed on a corresponding cluster node. Loading requests are sent to the execution nodes, thereby causing the execution nodes to start execution processes based on the corresponding loading requests. The execution processes start multiple model service frameworks on each cluster node. Multiple models are loaded onto each of the model service frameworks. Each loading request includes loading-tasks corresponding to the execution node to which the loading request was sent. The execution processes include a respective execution process for each model service framework.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority and is a continuation ofU.S. patent application Ser. No. 16/802,655, filed Feb. 27, 2020, whichis a continuation of PCT Application No. PCT/CN2020/071406, filed onJan. 10, 2020, which claims priority to Chinese Patent Application No.201910596970.5, filed on Jul. 3, 2019, and each application is herebyincorporated by reference in their entirety.

TECHNICAL FIELD

The present disclosure relates to the field of computer technologies,and in particular, to model loading.

BACKGROUND

With the rapid development of machine learning technologies, modelprediction has become an important online service. To provide modelprediction services, corresponding models need to be loaded into acluster node in advance.

In some existing systems, only one model service framework is started ona cluster node, and several models are loaded through the model serviceframework. However, when an exception occurs to the model serviceframework, the cluster node on which the model service framework islocated needs to be restarted. After the cluster node is restartedsuccessfully, the model service framework is restarted, and the modelsthat are already deployed on the cluster node are reloaded.

SUMMARY

In view of this, implementations of the present disclosure providemethods and systems, a control node, and an execution node for modelloading, to improve system availability.

According to a first aspect, an implementation of the present disclosureprovides a model loading method, including: determining, based on apreset execution script and resource information of several executionnodes, loading tasks corresponding to the execution nodes, wheredifferent execution nodes are deployed on different cluster nodes; andsending loading requests respectively to the several execution nodes, sothat the execution nodes start several execution processes based on thecorresponding loading requests, the several execution processes startseveral model service frameworks, and several models are loaded ontoeach of the model service frameworks, where the loading request includesloading tasks corresponding to the execution nodes, and the executionprocesses are in one-to-one correspondence with the model serviceframeworks.

According to a second aspect, an implementation of the presentdisclosure provides a model loading method, including: receiving aloading request sent by a control node, where the loading requestincludes loading task corresponding to execution nodes, the loadingtasks corresponding to the execution nodes are determined by the controlnode based on a preset execution script and resource information ofseveral execution nodes, and different execution nodes are deployed ondifferent cluster nodes; and starting several execution processes basedon the loading request, so that the several execution processes startseveral model service frameworks, and several models are loaded ontoeach of the model service frameworks, where the execution processes arein one-to-one correspondence with the model service frameworks.

According to a third aspect, an implementation of the present disclosureprovides a control node, including: a determining unit, configured todetermine, based on a preset execution script and resource informationof several execution nodes, loading tasks corresponding to the executionnodes, where different execution nodes are deployed on different clusternodes; and a sending unit, configured to send loading requestsrespectively to the several execution nodes, so that the execution nodesstart several execution processes based on the corresponding loadingrequests, the several execution processes start several model serviceframeworks, and several models are loaded onto each of the model serviceframeworks, where the loading request includes loading taskscorresponding to the execution nodes, and the execution processes are inone-to-one correspondence with the model service frameworks.

According to a fourth aspect, an implementation of the presentdisclosure provides an execution node, including: a receiving unit,configured to receive a loading request sent by a control node, wherethe loading request includes loading tasks corresponding to executionnodes, the loading tasks corresponding to the execution nodes aredetermined by the control node based on a preset execution script andresource information of several execution nodes, and different executionnodes are deployed on different cluster nodes; and a starting unit,configured to start several execution processes based on the loadingrequest, so that the several execution processes start several modelservice frameworks, and several models are loaded onto each of the modelservice frameworks, where the execution processes are in one-to-onecorrespondence with the model service frameworks.

According to a fifth aspect, an implementation of the present disclosureprovides a model loading system, including the control node according toany one of the previous implementations and the execution node accordingto any one of the previous implementations.

At least one of the previous technical solutions used in theimplementations of the present disclosure can achieve the followingbeneficial effects: In this method, several model service frameworks arestarted on each cluster node by an execution node deployed on differentcluster nodes, and several models are loaded through each model serviceframework. In this method, several model service frameworks can bedeployed on a cluster node; and when one model service framework isabnormal, the cluster node does not need to be restarted, and othermodel service frameworks in the cluster node can still work normally. Assuch, the system availability is improved.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the implementations of thepresent disclosure or the existing technology more clearly, thefollowing briefly introduces the accompanying drawings required fordescribing the implementations. Clearly, the accompanying drawings inthe following description are merely some implementations of the presentdisclosure, and a person of ordinary skill in the art can still deriveother drawings from these accompanying drawings without creativeefforts.

FIG. 1 is a flowchart illustrating a model loading method, according toan implementation of the present disclosure;

FIG. 2 is a flowchart illustrating a model loading method, according toanother implementation of the present disclosure;

FIG. 3 is a schematic structural diagram illustrating a control node,according to an implementation of the present specification; and

FIG. 4 is a schematic structural diagram illustrating an execution node,according to an implementation of the present specification;

FIG. 5 is a schematic structural diagram illustrating an execution node,according to another implementation of the present specification;

FIG. 6 is a flowchart illustrating a model loading system, according toan implementation of the present disclosure;

FIG. 7 is a flowchart illustrating a model loading method, according tostill another implementation of the present disclosure;

FIG. 8 is a schematic structural diagram illustrating a cluster,according to an implementation of the present specification; and

FIG. 9 is a schematic structural diagram illustrating a Ray-basedcluster, according to an implementation of the present specification.

DESCRIPTION OF IMPLEMENTATIONS

To make the objectives, technical solutions, and advantages of theimplementations of the present disclosure clearer, the following clearlyand comprehensively describes the technical solutions in theimplementations of the present disclosure with reference to theaccompanying drawings in the implementations of the present disclosure.Clearly, the described implementation are some but not all of theimplementations of the present disclosure. All other implementationsobtained by a person of ordinary skill in the art based on theimplementations of the present disclosure without creative efforts shallfall within the protection scope of the present disclosure.

In the conventional model loading method, only one model serviceframework is started on a cluster node, and several models are loadedthrough the model service framework. Different models are loaded ontothe same model service framework for deployment.

However, when the model service framework is abnormal, the cluster nodeon which the model service framework is located needs to be restarted.After the cluster node is restarted successfully, the model serviceframework is restarted, and the models that have been deployed on thecluster node are reloaded. In addition, the method is based on themachine granularity, that is, only one model service framework can bestarted on a cluster node, which leads to the waste of cluster noderesources. Further, a plurality of computationally intensive models areloaded onto the same model service framework, which leads to resourcepreemption and affects service performance.

In view of this, implementations of the present disclosure provide amodel loading method, where the method is applied to a control node. Asshown in FIG. 1, the method can include the following steps:

Step 101: Determine, based on a preset execution script and resourceinformation of several execution nodes, loading tasks corresponding tothe execution nodes, where different execution nodes are deployed ondifferent cluster nodes.

A cluster node is a unit in a cluster, has a relatively independentrunning environment, and can be at least one of a physical machine, avirtual machine, and a container.

An execution node is an independent process that is responsible for taskscheduling of a node.

A control node is an independent process that coordinates taskscheduling between different execution nodes globally.

An execution process is a user-level process that initiates a modelservice framework and manages the lifecycle of the model serviceframework.

A model service framework can be an HTTP framework or a Tensorflowframework, etc., where the Tensorflow framework is an open sourcemachine learning framework. The following implementations are describedby using the Tensorflow framework as an example.

The model service framework is started by an execution process, and isresponsible for executing a specific prediction calculation request, forexample, receiving feature data from a request, calculating a predictionscore and then returning the prediction score.

Resource information of an execution node includes the quantity of CPUcores of the cluster node on which the execution node is located, and/orthe remaining memory capacity of the cluster node on which the executionnode is located.

For each node in the cluster, a service can be deployed on the clusternode by running a deployment script on the node. A procedure fordeploying a service as follows: running a deployment script to deploy acontrol node, deploying an execution node on each cluster node,attaching each execution node to the control node, and reporting, byeach execution node, resource information to the control node.

Determining, based on a preset execution script and resource informationof several execution nodes, loading tasks corresponding to the executionnodes includes: determining the quantity of models corresponding to eachexecution node based on the total quantity of models declared in theexecution script, resource information corresponding to each model, andresource information of the several execution nodes. That is, theloading tasks corresponding to the execution nodes include the quantityof models corresponding to the execution node. Certainly, the loadingtasks corresponding to the execution nodes can also include thedeclaration about a model in the execution script and the declarationabout a model service framework in the execution script.

The resource information corresponding to the model refers to the memorycapacity corresponding to the model, that is, the memory capacityrequired to load the model.

It is worthwhile to note that model service frameworks declared in theexecution script can be of a same or different types. Similarly, modelsdeclared in the execution script can be of a same or different types.

For example, when the declared model service frameworks are of differenttypes, the models corresponding to each execution node and the quantityof the models are determined based on the total quantity of models ofdifferent types declared in the execution script, resource informationcorresponding to each model, and resource information of severalexecution nodes.

Step 102: Send loading requests respectively to the several executionnodes, so that the execution nodes start several execution processesbased on the corresponding loading requests, the several executionprocesses start several model service frameworks, and several models areloaded onto each of the model service frameworks, where the loadingrequest includes loading tasks corresponding to the execution nodes, andthe execution processes are in one-to-one correspondence with the modelservice frameworks.

In this method, several model service frameworks are started on eachcluster node by an execution node deployed on different cluster nodes,and several models are loaded through each model service framework. Inthis method, at least two model service frameworks can be deployed on acluster node; and when one model service framework is abnormal, thecluster node does not need to be restarted, and other model serviceframeworks in the cluster node can still work normally. As such, thesystem availability is improved.

In an implementation of the present disclosure, one model is loaded ontoeach model service framework to reduce resource consumption.

As shown in FIG. 2, an implementation of the present disclosure providesa model loading method, where the method is applied to an execution nodeand includes:

Step 201: Receive a loading request sent by a control node, where theloading request includes loading task corresponding to execution nodes,the loading tasks corresponding to the execution nodes are determined bythe control node based on a preset execution script and resourceinformation of several execution nodes, and different execution nodesare deployed on different cluster nodes.

Step 202: Start several execution processes based on the loadingrequest, so that the several execution processes start several modelservice frameworks, and several models are loaded onto each of the modelservice frameworks, where the execution processes are in one-to-onecorrespondence with the model service frameworks.

In an implementation of the present disclosure, the loading requestfurther includes a declaration about an execution process in anexecution script; and

Starting several execution processes based on the loading requestincludes: starting several execution processes based on a declarationabout an execution process in the execution script.

In an implementation of the present disclosure, the loading requestfurther includes a declaration about a model service framework in theexecution script; and starting several model service frameworks by theseveral execution processes includes: starting, by the several executionprocesses, the several model service frameworks based on the declarationabout a model service framework in the execution script.

In an implementation of the present disclosure, to further improve thesystem availability, the method further includes: when it is detected,through monitoring, that a target execution process in the severalexecution processes is lost, re-establishing the target executionprocess.

As shown in FIG. 3, an implementation of the present disclosure providesa control node, including: a determining unit 301, configured todetermine, based on a preset execution script and resource informationof several execution nodes, loading tasks corresponding to the executionnodes, where different execution nodes are deployed on different clusternodes; and a sending unit 302, configured to send loading requestsrespectively to the several execution nodes, so that the execution nodesstart several execution processes based on the corresponding loadingrequests, the several execution processes start several model serviceframeworks, and several models are loaded onto each of the model serviceframeworks, where the loading request includes loading taskscorresponding to the execution nodes, and the execution processes are inone-to-one correspondence with the model service frameworks.

In an implementation of the present disclosure, the determining unit 301is configured to determine the quantity of models corresponding to eachexecution node based on the total quantity of models declared in theexecution script, resource information corresponding to each model, andresource information of the several execution nodes.

In an implementation of the present disclosure, a cluster node includesat least one of a physical machine, a virtual machine, and a container.

In an implementation of the present disclosure, resource information ofan execution node includes the quantity of CPU cores of the cluster nodeon which the execution node is located, and/or the remaining memorycapacity of the cluster node on which the execution node is located.

As shown in FIG. 4, an implementation of the present disclosure providesan execution node, including: a receiving unit 401, configured toreceive a loading request sent by a control node, where the loadingrequest includes loading tasks corresponding to execution nodes, theloading tasks corresponding to the execution nodes are determined by thecontrol node based on a preset execution script and resource informationof several execution nodes, and different execution nodes are deployedon different cluster nodes; and a starting unit 402, configured to startseveral execution processes based on the loading request, so that theseveral execution processes start several model service frameworks, andseveral models are loaded onto each of the model service frameworks,where the execution processes are in one-to-one correspondence with themodel service frameworks.

In an implementation of the present disclosure, as shown in FIG. 5, theexecution node further includes a monitoring unit 403.

The monitoring unit 403 is configured to: when it is detected, throughmonitoring, that a target execution process in the several executionprocesses is lost, re-establish the target execution process.

In an implementation of the present disclosure, the loading requestfurther includes a declaration about an execution process in anexecution script; and the starting unit 402 is configured to startseveral execution processes based on a declaration about an executionprocess in the execution script.

In an implementation of the present disclosure, the loading requestfurther includes a declaration about a model service framework in theexecution script; and the starting unit 402 is configured to enable theseveral execution processes to start the several model serviceframeworks based on the declaration about a model service framework inthe execution script.

In an implementation of the present disclosure, a cluster node includesat least one of a physical machine, a virtual machine, and a container.

In an implementation of the present disclosure, resource information ofan execution node includes the quantity of CPU cores of the cluster nodeon which the execution node is located, and/or the remaining memorycapacity of the cluster node on which the execution node is located.

As shown in FIG. 6, an implementation of the present disclosure providesa model loading system, including the control node 601 according to anyone of the previous implementations and the execution node 602 accordingto any one of the previous implementations.

The quantity of execution nodes in the model loading system can be setbased on an actual requirement. For example, the model loading systemincludes a control node 601 and two execution nodes 602.

As shown in FIG. 7, in this implementation of the present disclosure,the cluster shown in FIG. 8 is used as an example to describe the modelloading method in detail. The method includes the following steps:

Step 701: A control node determines, based on a preset execution scriptand resource information of three execution nodes, loading taskscorresponding to the execution nodes, where different execution nodesare deployed on different physical machines.

The cluster shown in FIG. 8 includes physical machine 1, physicalmachine 2, physical machine 3, and physical machine 4. The control nodesare deployed on physical machine 1; and the three execution nodes aredeployed on physical machine 2, physical machine 3, and physical machine4 respectively.

The execution script declares the model service framework, the quantityof model service frameworks, execution processes, models, the totalquantity of models, and resource information corresponding to eachmodel.

In this implementation of the present disclosure, the model serviceframeworks are Tensorflow frameworks, the quantity of Tensorflowframeworks is 9, two identical models are loaded onto each Tensorflowframework, and the total quantity of models is 18.

The quantity of models corresponding to each execution node isdetermined based on the remaining memory capacity of the cluster node onwhich each execution node is located, the memory capacity correspondingto each model, and the total quantity of models. In this implementationof the present disclosure, the loading task corresponding to anexecution node includes the quantity of models corresponding to theexecution node.

Assuming that loading tasks are assigned to three execution nodes, eachexecution node corresponds to six models.

Step 702: The control node sends loading requests to the three executionnodes, where for each execution node, the loading request includes adeclaration about a model corresponding to the execution node, theloading tasks corresponding to the execution node, the declaration aboutan execution process in the execution script, the declaration about aTensorflow framework corresponding to the execution node, and thequantity of Tensorflow frameworks corresponding to the execution node.

In an actual application scenario, the declaration about a modelcorresponding to the execution node, the declaration about an executionprocess in the execution script, the declaration about a Tensorflowframework corresponding to the execution node, and the quantity ofTensorflow frameworks corresponding to the execution node can also beincluded in the loading tasks corresponding to the execution nodes.

In this implementation of the present disclosure, content of the loadingrequests received by the execution nodes is the same. The loadingrequest of only one execution node is used as an example for descriptionbelow. The loading request includes: the declaration about Tensorflowframework corresponding to the execution node, the quantity ofTensorflow frameworks corresponding to the execution node (which is 3),the declaration about an execution process in the execution script, thedeclaration about a model corresponding to the execution node, and thequantity of models corresponding to the execution node (which is 6).

Step 703: The execution nodes receive the loading request sent by thecontrol node.

Step 704: The execution nodes start several execution processes based ondeclarations about execution processes in the execution script and thequantity of Tensorflow frameworks corresponding to the execution nodes.

The quantity of Tensorflow frameworks corresponding to execution nodesis equal to the quantity of execution processes.

Step 705: Several execution processes start several Tensorflowframeworks based on the declarations about Tensorflow frameworkscorresponding to the execution nodes, where the execution processes arein one-to-one correspondence with the Tensorflow frameworks.

The execution process starts the Tensorflow framework based on thedeclaration about a Tensorflow framework corresponding to the executionnode.

Step 706: Several models are loaded onto each Tensorflow framework basedon the declarations about models corresponding to the execution nodesand the loading tasks corresponding to the execution nodes.

Several models are loaded to the Tensorflow framework based on the modelcorresponding to the execution node and the loading tasks correspondingto the execution nodes (that is, the quantity of models corresponding tothe execution node).

In this implementation of the present disclosure, two models are loadedonto each Tensorflow framework.

Step 707: When it is detected, through monitoring, that a targetexecution process in the several execution processes is lost, theexecution node re-establishes the target execution process.

Each execution node can monitor the running status of the executionprocess. When the target execution process is lost, the target executionprocess can be re-established in time, which can reduce the impact ofthe lost target execution process on the model prediction process.

When there are many types of model service frameworks and many types ofto-be-loaded models, the execution script declares various model serviceframeworks, the quantity of model service frameworks of each type, theexecution process corresponding to each model service framework, variousmodels, the total quantity of models, and the resource informationcorresponding to each model. The execution script can also declareinformation such as the quantity of models of each type, etc.

Correspondingly, the loading request received by the execution nodeincludes the declaration about a model service framework correspondingto the execution node, the quantity of model service frameworks of eachtype that are corresponding to the execution node, the declaration aboutan execution process corresponding to the execution node, thedeclaration about a model corresponding to the execution node, and thequantity of models of each type that are corresponding to the executionnode.

In an actual application scenario, technicians can change theimplementation script to scale up or scale down the model serviceframework or make the service model framework online or offline, todynamically adjust the model service framework. In this method,lightweight resource isolation is provided by the execution process, toensure exclusive use of the resource and avoid the resource preemptionproblem when all models on a cluster node are loaded onto a single modelservice framework. In this method, the execution node can monitor theexecution process, and the execution process can be established when theexecution process is lost. As such, when the model service frameworkfails, the model service framework can be automatically restarted in alightweight manner without the need of restarting the cluster node onwhich the model service framework is located.

In an actual application scenario, the method and device provided in theprevious implementations can be implemented based on an open sourcedistributed execution engine Ray. In this case, the service is a Rayservice; the execution script is a Driver script; the control node is aRay head node; the execution node is a Ray node; and the executionprocess is a ray-actor. The cluster shown in FIG. 9 corresponds to thecluster shown in FIG. 8 and is a Ray-based cluster.

The Ray head node is a head node of the Ray service; the ray-actor isthe resource encapsulation defined for the Ray service; the Driverscript is a user-defined execution script based on the Ray API and theTensorflow API; and the Driver script declares, based on the Ray API,the total quantity of models and resource information corresponding toeach model. The Driver script can also declare a ray-actor, a modelservice framework, etc., based on the Ray API.

In the 1990s, whether a technology improvement is a hardware improvement(for example, improvement of a circuit structure, such as a diode, atransistor, or a switch) or a software improvement (improvement of amethod or a procedure) can be obviously distinguished. However, astechnologies develop, the current improvement for many method procedurescan be considered as a direct improvement of a hardware circuitstructure. A designer usually programs an improved method procedure to ahardware circuit, to obtain a corresponding hardware circuit structure.Therefore, a method procedure can be improved by using a hardware entitymodule. For example, a programmable logic device (PLD) (for example, afield programmable gate array (FPGA)) is such an integrated circuit, anda logical function of the programmable logic device is determined by auser through device programming. The designer performs programming to“integrate” a digital system to a PLD without requesting a chipmanufacturer to design and produce an application-specific integratedcircuit chip. In addition, at present, instead of manually manufacturingan integrated chip, this type of programming is mostly implemented byusing “logic compiler” software. The programming is similar to asoftware compiler used to develop and write a program. Original codeneeds to be written in a particular programming language forcompilation. The language is referred to as a hardware descriptionlanguage (HDL). There are many HDLs, such as the Advanced BooleanExpression Language (ABEL), the Altera Hardware Description Language(AHDL), Confluence, the Cornell University Programming Language (CUPL),HDCal, the Java Hardware Description Language (JHDL), Lava, Lola, MyHDL,PALASM, and the Ruby Hardware Description Language (RHDL), etc. Thevery-high-speed integrated circuit hardware description language (VHDL)and Verilog are most commonly used. A person skilled in the art shouldalso understand that a hardware circuit that implements a logical methodprocedure can be readily obtained once the method procedure is logicallyprogrammed by using the several described hardware description languagesand is programmed into an integrated circuit.

A controller can be implemented by using any appropriate method. Forexample, the controller can be a microprocessor or a processor, or acomputer-readable medium that stores computer readable program code(such as software or firmware) that can be executed by themicroprocessor or the processor, a logic gate, a switch, anapplication-specific integrated circuit (ASIC), a programmable logiccontroller, or a built-in microprocessor. Examples of the controllerinclude but are not limited to the following microprocessors: ARC 625D,Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. Thememory controller can also be implemented as a part of the control logicof the memory. A person skilled in the art also knows that, in additionto implementing the controller by using the computer readable programcode, logic programming can be performed on method steps to allow thecontroller to implement the same function in forms of the logic gate,the switch, the application-specific integrated circuit, theprogrammable logic controller, and the built-in microcontroller.Therefore, the controller can be considered as a hardware component, anda device configured to implement various functions in the controller canalso be considered as a structure in the hardware component.Alternatively, the device configured to implement various functions caneven be considered as both a software module implementing the method anda structure in the hardware component.

The system, device, module, or unit illustrated in the previousimplementations can be implemented by using a computer chip or anentity, or can be implemented by using a product having a certainfunction. A typical implementation device is a computer. A specific formof the computer can be a personal computer, a laptop computer, acellular phone, a camera phone, an intelligent phone, a personal digitalassistant, a media player, a navigation device, an email transceiverdevice, a game console, a tablet computer, a wearable device, or anycombination thereof.

For convenience of description, the above devices are describedseparately in terms of their functions. Certainly, functions of theunits can be implemented in the same or different software and/orhardware when the present specification is implemented.

A person skilled in the art should understand that the implementationsof the present specification can be provided as methods, systems, orcomputer program products. Therefore, the present specification can takea form of complete hardware implementations, complete softwareimplementations, or implementations combining software and hardware.Further, the present specification can take a form of a computer programproduct implemented on one or more computer-usable storage media(including but not limited to disk storage, CD-ROM, and optical storage,etc.) containing computer-usable program code.

The present specification is described with reference to the flowchartsand/or block diagrams of the method, the device (system), and thecomputer program product according to the implementations of the presentspecification. It is worthwhile to note that computer programinstructions can be used to implement each process and/or each block inthe flowcharts and/or the block diagrams and a combination of a processand/or a block in the flowcharts and/or the block diagrams. Thesecomputer program instructions can be provided for a general-purposecomputer, a dedicated computer, an embedded processor, or a processor ofanother programmable data processing device to generate a machine, sothe instructions executed by the computer or the processor of theanother programmable data processing device generate a device forimplementing a specific function in one or more processes in theflowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions can be stored in a computer readablememory that can instruct the computer or the another programmable dataprocessing device to work in a specific manner, so the instructionsstored in the computer readable memory generate an artifact thatincludes an instruction device. The instruction device implements aspecific function in one or more processes in the flowcharts and/or inone or more blocks in the block diagrams.

These computer program instructions can be loaded onto the computer oranother programmable data processing device, so that a series ofoperations and steps are performed on the computer or the anotherprogrammable device, thereby generating computer-implemented processing.Therefore, the instructions executed on the computer or anotherprogrammable device provide steps for implementing a specific functionin one or more processes in the flowcharts and/or in one or more blocksin the block diagrams.

In a typical configuration, a computing device includes one or moreprocessors (CPUs), an input/output interface, a network interface, and amemory.

The memory can include a non-persistent memory, a random access memory(RAM), a non-volatile memory, and/or another form that are in a computerreadable medium, for example, a read-only memory (ROM) or a flash memory(flash RAM). The memory is an example of the computer readable medium.

The computer readable medium includes persistent, non-persistent,movable, and unmovable media that can store information by using anymethod or technology. The information can be a computer readableinstruction, a data structure, a program module, or other data. Examplesof the computer storage medium include but are not limited to a phasechange random access memory (PRAM), a static random access memory(SRAM), a dynamic random access memory (DRAM), another type of RAM, aROM, an electrically erasable programmable read-only memory (EEPROM), aflash memory or another memory technology, a compact disc read-onlymemory (CD-ROM), a digital versatile disc (DVD) or another opticalstorage, a cassette magnetic tape, a magnetic tape/magnetic diskstorage, another magnetic storage device, or any other non-transmissionmedium. The computer storage medium can be used to store informationaccessible by a computing device. Based on the definition in the presentspecification, the computer readable medium does not include transitorymedia such as a modulated data signal and carrier.

It is worthwhile to note that terms “include”, “comprise” or any othervariant is intended to cover non-exclusive inclusion, so that processes,methods, commodities or devices that include a series of elementsinclude not only those elements but also other elements that are notexplicitly listed, or elements inherent in such processes, methods,commodities or devices. An element described by “includes a . . . ”further includes, without more constraints, another identical element inthe process, method, product, or device that includes the element.

The present specification can be described in the general context ofcomputer executable instructions executed by a computer, for example, aprogram module. Generally, the program module includes a routine, aprogram, an object, a component, a data structure, etc. executing aspecific task or implementing a specific abstract data type. The presentspecification can also be practiced in distributed computingenvironments. In the distributed computing environments, tasks areperformed by remote processing devices connected through acommunications network. In a distributed computing environment, theprogram module can be located in both local and remote computer storagemedia including storage devices.

It is worthwhile to note that the implementations of the presentspecification are described in a progressive way. For same or similarparts of the implementations, mutual references can be made to theimplementations. Each implementation focuses on a difference from theother implementations. Particularly, a system implementation isbasically similar to a method implementation, and therefore is describedbriefly. For related parts, references can be made to relateddescriptions in the method implementation.

The described descriptions are merely examples of the presentspecification and are not intended to limit the present application. Fora person skilled in the art, the present application may be subject tovarious modifications and variations. Any modification, equivalentreplacement or improvement made within spirit and principles of thepresent application shall be included in claims of the presentapplication.

1.-20. (canceled)
 21. A computer-implemented method, comprising:receiving, by an execution node from a control node, a loading requestcomprising loading tasks corresponding to execution nodes, wherein theloading tasks are determined by the control node based on a presetexecution script and resource information for each of a plurality ofexecution nodes, and wherein different execution nodes are deployed ondifferent cluster nodes; and starting, by the execution node, multipleexecution processes based on the loading request, wherein the multipleexecution processes start multiple model service frameworks and multiplemodels are loaded onto each of the model service frameworks.
 22. Thecomputer-implemented method of claim 21, wherein the execution processesare in one-to-one correspondence with the model service frameworks. 23.The computer-implemented method of claim 21, further comprising:detecting that a target execution process has been lost; and in responseto detecting that the target execution process has been lost,re-establishing the target execution process.
 24. Thecomputer-implemented method of claim 21, wherein: the loading requestfurther comprises a declaration about an execution process in the presetexecution script; and starting multiple execution processes based on theloading request comprises starting the multiple execution processesbased on the declaration about the execution process in the presetexecution script.
 25. The computer-implemented method of claim 21,wherein: the loading request further comprises a declaration about amodel service framework in the preset execution script; and startingmultiple model service frameworks by the multiple execution processescomprises starting the multiple model service frameworks based on thedeclaration about the model service framework in the preset executionscript.
 26. The computer-implemented method of claim 21, wherein eachcluster node comprises at least one of a physical machine, a virtualmachine, or a container.
 27. The computer-implemented method of claim21, wherein the resource information for each particular execution nodecomprises a least one of a quantity of central processing unit (CPU)cores of a particular cluster node on which the particular executionnode is located or remaining memory capacity of the particular clusternode on which the particular execution node is located.
 28. Anon-transitory, computer-readable medium storing one or moreinstructions executable by a computer system to perform operationscomprising: receiving, by an execution node from a control node, aloading request comprising loading tasks corresponding to executionnodes, wherein the loading tasks are determined by the control nodebased on a preset execution script and resource information for each ofa plurality of execution nodes, and wherein different execution nodesare deployed on different cluster nodes; and starting, by the executionnode, multiple execution processes based on the loading request, whereinthe multiple execution processes start multiple model service frameworksand multiple models are loaded onto each of the model serviceframeworks.
 29. The non-transitory, computer-readable medium of claim28, wherein the execution processes are in one-to-one correspondencewith the model service frameworks.
 30. The non-transitory,computer-readable medium of claim 28, wherein the operations comprise:detecting that a target execution process has been lost; and in responseto detecting that the target execution process has been lost,re-establishing the target execution process.
 31. The non-transitory,computer-readable medium of claim 28, wherein: the loading requestfurther comprises a declaration about an execution process in the presetexecution script; and starting multiple execution processes based on theloading request comprises starting the multiple execution processesbased on the declaration about the execution process in the presetexecution script.
 32. The non-transitory, computer-readable medium ofclaim 28, wherein: the loading request further comprises a declarationabout a model service framework in the preset execution script; andstarting multiple model service frameworks by the multiple executionprocesses comprises starting the multiple model service frameworks basedon the declaration about the model service framework in the presetexecution script.
 33. The non-transitory, computer-readable medium ofclaim 28, wherein each cluster node comprises at least one of a physicalmachine, a virtual machine, or a container.
 34. A computer-implementedsystem, comprising: one or more computers; and one or more computermemory devices interoperably coupled with the one or more computers andhaving tangible, non-transitory, machine-readable media storing one ormore instructions that, when executed by the one or more computers,perform one or more operations comprising: receiving, by an executionnode from a control node, a loading request comprising loading taskscorresponding to execution nodes, wherein the loading tasks aredetermined by the control node based on a preset execution script andresource information for each of a plurality of execution nodes, andwherein different execution nodes are deployed on different clusternodes; and starting, by the execution node, multiple execution processesbased on the loading request, wherein the multiple execution processesstart multiple model service frameworks and multiple models are loadedonto each of the model service frameworks.
 35. The computer-implementedsystem of claim 34, wherein the execution processes are in one-to-onecorrespondence with the model service frameworks.
 36. Thecomputer-implemented system of claim 34, wherein the operationscomprise: detecting that a target execution process has been lost; andin response to detecting that the target execution process has beenlost, re-establishing the target execution process.
 37. Thecomputer-implemented system of claim 34, wherein: the loading requestfurther comprises a declaration about an execution process in the presetexecution script; and starting multiple execution processes based on theloading request comprises starting the multiple execution processesbased on the declaration about the execution process in the presetexecution script.
 38. The computer-implemented system of claim 34,wherein: the loading request further comprises a declaration about amodel service framework in the preset execution script; and startingmultiple model service frameworks by the multiple execution processescomprises starting the multiple model service frameworks based on thedeclaration about the model service framework in the preset executionscript.
 39. The computer-implemented system of claim 34, wherein eachcluster node comprises at least one of a physical machine, a virtualmachine, or a container.
 40. The computer-implemented system of claim34, wherein the resource information for each particular execution nodecomprises a least one of a quantity of CPU cores of a particular clusternode on which the particular execution node is located or remainingmemory capacity of the particular cluster node on which the particularexecution node is located.